Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04cb627986bfc02d2596eb013f3a14f4ad04e1678436d49a1021a7ac57f52dce

Tx prefix hash: bb4f2c995ed83c335c3986389a7b905a7ff0d8b0a582d4d482dcbb5f5c1afebd
Tx public key: daccd16298764d8d908ed31e3f3f3656925de4469c07fc20fee1c991e3111789
Timestamp: 1737770510 Timestamp [UCT]: 2025-01-25 02:01:50 Age [y:d:h:m:s]: 00:143:14:28:21
Block: 1204692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102372 RingCT/type: yes/0
Extra: 01daccd16298764d8d908ed31e3f3f3656925de4469c07fc20fee1c991e3111789021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9bf7895dfa1567a3664da0cb1e52a2d2f0e81ce63d6c03559677b58a95dfaa8 0.600000000000 1691383 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": 1204702, "vin": [ { "gen": { "height": 1204692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9bf7895dfa1567a3664da0cb1e52a2d2f0e81ce63d6c03559677b58a95dfaa8" } } ], "extra": [ 1, 218, 204, 209, 98, 152, 118, 77, 141, 144, 142, 211, 30, 63, 63, 54, 86, 146, 93, 228, 70, 156, 7, 252, 32, 254, 225, 201, 145, 227, 17, 23, 137, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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