Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 189771f0377d20fab3f2e8d4143b61d8d8fdb765618eb626f5258ed1d0291f00

Tx prefix hash: 1fc655744ee1d365ffb9e653813740a4afcb43c4cf7b0742c0bb5369d575ed23
Tx public key: eee73f64fce8ad85bee2a9d38fc37e95a9f67307b991d5b30d2b8bbe32275ae2
Timestamp: 1696134392 Timestamp [UCT]: 2023-10-01 04:26:32 Age [y:d:h:m:s]: 02:101:13:23:17
Block: 859903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592304 RingCT/type: yes/0
Extra: 01eee73f64fce8ad85bee2a9d38fc37e95a9f67307b991d5b30d2b8bbe32275ae2021100000001bfa22221000000000000000000

1 output(s) for total of 0.868529233000 dcy

stealth address amount amount idx
00: a11463995f492592d5cb399656fe777e6bb359919f7010b2ab39470da20e8a40 0.868529233000 1314155 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": 859913, "vin": [ { "gen": { "height": 859903 } } ], "vout": [ { "amount": 868529233, "target": { "key": "a11463995f492592d5cb399656fe777e6bb359919f7010b2ab39470da20e8a40" } } ], "extra": [ 1, 238, 231, 63, 100, 252, 232, 173, 133, 190, 226, 169, 211, 143, 195, 126, 149, 169, 246, 115, 7, 185, 145, 213, 179, 13, 43, 139, 190, 50, 39, 90, 226, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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