Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9accd0e4c79f66a2d4124c9cbfaa48664200c1eda401a2924d4391f7f198f72

Tx prefix hash: a100f98829329a024b3a204e88a63354b09f8c21fc4c4fc7524546d69fb48501
Tx public key: 254df4b5acf0c0ed19b8d890c3af8fa07ffca828d8735cf876f1e6426f164072
Timestamp: 1725569007 Timestamp [UCT]: 2024-09-05 20:43:27 Age [y:d:h:m:s]: 00:080:05:09:57
Block: 1103730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57350 RingCT/type: yes/0
Extra: 01254df4b5acf0c0ed19b8d890c3af8fa07ffca828d8735cf876f1e6426f16407202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3973a6fe5ff45ea8c5bd51f557db59523b059d74f983324d59f6f712a344976b 0.600000000000 1580671 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": 1103740, "vin": [ { "gen": { "height": 1103730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3973a6fe5ff45ea8c5bd51f557db59523b059d74f983324d59f6f712a344976b" } } ], "extra": [ 1, 37, 77, 244, 181, 172, 240, 192, 237, 25, 184, 216, 144, 195, 175, 143, 160, 127, 252, 168, 40, 216, 115, 92, 248, 118, 241, 230, 66, 111, 22, 64, 114, 2, 17, 0, 0, 0, 2, 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