Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8e51253e6dcb003bba29979766b291ca1b0f037a649d10c2be4ca744bde6ffc

Tx prefix hash: 544ba7177771a8fe09b02f37c33bc0614c6350efe50b88e86cd02f80312032ad
Tx public key: 9f412e8b8c994067188c7d21b95de2a2fa90fea0fed11bd3fd517142163c29c0
Timestamp: 1699151152 Timestamp [UCT]: 2023-11-05 02:25:52 Age [y:d:h:m:s]: 01:085:20:43:20
Block: 884965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322284 RingCT/type: yes/0
Extra: 019f412e8b8c994067188c7d21b95de2a2fa90fea0fed11bd3fd517142163c29c002110000000533af99f4000000000000000000

1 output(s) for total of 0.717370633000 dcy

stealth address amount amount idx
00: 7ad8f6387c24abe8bd5a69bf0b8cba390898481a95aee874a13679c011e66d0a 0.717370633000 1340714 of 0

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": 884975, "vin": [ { "gen": { "height": 884965 } } ], "vout": [ { "amount": 717370633, "target": { "key": "7ad8f6387c24abe8bd5a69bf0b8cba390898481a95aee874a13679c011e66d0a" } } ], "extra": [ 1, 159, 65, 46, 139, 140, 153, 64, 103, 24, 140, 125, 33, 185, 93, 226, 162, 250, 144, 254, 160, 254, 209, 27, 211, 253, 81, 113, 66, 22, 60, 41, 192, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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