Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23ce67dc2250ca753a966bc9bb034544b0e7c787d78ae0587320a021cc104a06

Tx prefix hash: bb9c307fd65a5b6ad27ce9d2f6e21b8a06591ddbb4f37ff512a83943ae92d520
Tx public key: 7bb85d727a5b024a184596edf7a4f91d6949256d27edf2008ee9a308b356c9a6
Timestamp: 1731396872 Timestamp [UCT]: 2024-11-12 07:34:32 Age [y:d:h:m:s]: 00:140:03:04:05
Block: 1151946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99970 RingCT/type: yes/0
Extra: 017bb85d727a5b024a184596edf7a4f91d6949256d27edf2008ee9a308b356c9a60211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 170b6f29e200fabd383557e99eea923a29c271868664f5da80d1554fba47d1c0 0.600000000000 1637535 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": 1151956, "vin": [ { "gen": { "height": 1151946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "170b6f29e200fabd383557e99eea923a29c271868664f5da80d1554fba47d1c0" } } ], "extra": [ 1, 123, 184, 93, 114, 122, 91, 2, 74, 24, 69, 150, 237, 247, 164, 249, 29, 105, 73, 37, 109, 39, 237, 242, 0, 142, 233, 163, 8, 179, 86, 201, 166, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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