Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aa09f38c8888ce0f912affb2121af2d9f7d3649c76e21d8539cab7fa1428919

Tx prefix hash: 4c1a4152da48aff43cc4cbaaca89eeb6df3e992427ebdc15e899dc7699f29701
Tx public key: 0fc7ae04f7944c6cb76dc70075147523d36e4fb0682ec02fe326d48dec540f3a
Timestamp: 1705403125 Timestamp [UCT]: 2024-01-16 11:05:25 Age [y:d:h:m:s]: 01:154:01:09:43
Block: 936524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371128 RingCT/type: yes/0
Extra: 010fc7ae04f7944c6cb76dc70075147523d36e4fb0682ec02fe326d48dec540f3a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bd73aa0003bc4745efd5fec6f84c866a75cb4775e7785bbbdaec7e83c8c3496 0.600000000000 1394552 of 15

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": 936534, "vin": [ { "gen": { "height": 936524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bd73aa0003bc4745efd5fec6f84c866a75cb4775e7785bbbdaec7e83c8c3496" } } ], "extra": [ 1, 15, 199, 174, 4, 247, 148, 76, 108, 183, 109, 199, 0, 117, 20, 117, 35, 211, 110, 79, 176, 104, 46, 192, 47, 227, 38, 212, 141, 236, 84, 15, 58, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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