Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d7a0d7f14277a13384f52810c2815d98d1768957821addf1098278b394390a4b

Tx prefix hash: f74186911142232d0d8d65ad15267198d678c8075b2cf6f10acd22be2d2f0f40
Tx public key: e1fa81b2e4bc9d9ef675b8f514fca1ef9409c6d235323e2b62e74a95709a6c0b
Timestamp: 1578254473 Timestamp [UCT]: 2020-01-05 20:01:13 Age [y:d:h:m:s]: 04:356:12:35:52
Block: 39430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144045 RingCT/type: yes/0
Extra: 01e1fa81b2e4bc9d9ef675b8f514fca1ef9409c6d235323e2b62e74a95709a6c0b02110000000149b77a3d000000000000000000

1 output(s) for total of 454.320471321000 dcy

stealth address amount amount idx
00: bebf89e1554c06192a553531f288eaa0d17d441003359295861497db276fcd76 454.320471321000 68016 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 39440, "vin": [ { "gen": { "height": 39430 } } ], "vout": [ { "amount": 454320471321, "target": { "key": "bebf89e1554c06192a553531f288eaa0d17d441003359295861497db276fcd76" } } ], "extra": [ 1, 225, 250, 129, 178, 228, 188, 157, 158, 246, 117, 184, 245, 20, 252, 161, 239, 148, 9, 198, 210, 53, 50, 62, 43, 98, 231, 74, 149, 112, 154, 108, 11, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8