Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd7e57589b84186e7c2f6521e41d3ec78b90d040ece51f69c45bdaff1fb33ff6

Tx prefix hash: 0bfd215c236e2c76e75cd0b361b252548512a7a0a07758c48ac5f1dbd313cefc
Tx public key: f8ff1d0a26e4a518fcc3c5683ae29a56dfe663ede554637081bbd97f7fce8a2a
Timestamp: 1638914982 Timestamp [UCT]: 2021-12-07 22:09:42 Age [y:d:h:m:s]: 03:097:17:49:18
Block: 390643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 848587 RingCT/type: yes/0
Extra: 01f8ff1d0a26e4a518fcc3c5683ae29a56dfe663ede554637081bbd97f7fce8a2a021100000006e59f5d07000000000000000000

1 output(s) for total of 31.162905486000 dcy

stealth address amount amount idx
00: 770db6c3f6c5a737de14dbc39f10b2f22c07b8f7d78e96844b384a70178adf17 31.162905486000 786540 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": 390653, "vin": [ { "gen": { "height": 390643 } } ], "vout": [ { "amount": 31162905486, "target": { "key": "770db6c3f6c5a737de14dbc39f10b2f22c07b8f7d78e96844b384a70178adf17" } } ], "extra": [ 1, 248, 255, 29, 10, 38, 228, 165, 24, 252, 195, 197, 104, 58, 226, 154, 86, 223, 230, 99, 237, 229, 84, 99, 112, 129, 187, 217, 127, 127, 206, 138, 42, 2, 17, 0, 0, 0, 6, 229, 159, 93, 7, 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