Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19ac39a6a34b6bc0bfc2151d83eccce3bedb4e33886c3c6f075c750a848519a4

Tx prefix hash: db4ef7b4fdacd99ea56993be96e31eff23f56bb6b8d7f077fd04914d4aa6a12b
Tx public key: 915ada4e35d5a46ac3bb18a220cab9148da807039fe9faf1997aa18ab4e0bd61
Timestamp: 1728728971 Timestamp [UCT]: 2024-10-12 10:29:31 Age [y:d:h:m:s]: 00:212:20:41:57
Block: 1129928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151934 RingCT/type: yes/0
Extra: 01915ada4e35d5a46ac3bb18a220cab9148da807039fe9faf1997aa18ab4e0bd6102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79b4d9bb75c50a7e2ff9eae66411af9ce80006797de3b3f6f92daf68f12f7c62 0.600000000000 1612799 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": 1129938, "vin": [ { "gen": { "height": 1129928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79b4d9bb75c50a7e2ff9eae66411af9ce80006797de3b3f6f92daf68f12f7c62" } } ], "extra": [ 1, 145, 90, 218, 78, 53, 213, 164, 106, 195, 187, 24, 162, 32, 202, 185, 20, 141, 168, 7, 3, 159, 233, 250, 241, 153, 122, 161, 138, 180, 224, 189, 97, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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