Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba7caa5d19437341e525e52e38a0a6431adcb593688bc1c4d8fc0ee76922c4d2

Tx prefix hash: ac1e6215db701529ef389141e3d19499b7db21433c201d81717dc8eae0afdf1d
Tx public key: 423be8e5831a4cd9624657decd39f4ef83187f7a40f77445f000b47498fe0fda
Timestamp: 1733993629 Timestamp [UCT]: 2024-12-12 08:53:49 Age [y:d:h:m:s]: 00:188:14:56:13
Block: 1173487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134489 RingCT/type: yes/0
Extra: 01423be8e5831a4cd9624657decd39f4ef83187f7a40f77445f000b47498fe0fda021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e0bf001efae9f25175e5af2e9bde3a68d1a830f0c881df926e0ebd1c106ebe3 0.600000000000 1659516 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": 1173497, "vin": [ { "gen": { "height": 1173487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e0bf001efae9f25175e5af2e9bde3a68d1a830f0c881df926e0ebd1c106ebe3" } } ], "extra": [ 1, 66, 59, 232, 229, 131, 26, 76, 217, 98, 70, 87, 222, 205, 57, 244, 239, 131, 24, 127, 122, 64, 247, 116, 69, 240, 0, 180, 116, 152, 254, 15, 218, 2, 17, 0, 0, 0, 1, 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