Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4564c3bc09a5bd52c0970a9ff2799dbbfbdeb53c4e51c818b801c1f660dfe430

Tx prefix hash: 178f566c3038a38a479cc37cf28d2c704742681a804e02408d6096a731fa0d23
Tx public key: b34638c933dd47f2f2d99fabe834dfec009d3e5d9cb379e2ebd68fe5f5f56193
Timestamp: 1673111645 Timestamp [UCT]: 2023-01-07 17:14:05 Age [y:d:h:m:s]: 02:161:04:02:23
Block: 669684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636814 RingCT/type: yes/0
Extra: 01b34638c933dd47f2f2d99fabe834dfec009d3e5d9cb379e2ebd68fe5f5f5619302110000000252542ceb000000000000000000

1 output(s) for total of 3.707309693000 dcy

stealth address amount amount idx
00: bf1b59a6f7e408c3d7281769948afed7c58a0aaf673b7c297a682b86e4a97bb9 3.707309693000 1111037 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": 669694, "vin": [ { "gen": { "height": 669684 } } ], "vout": [ { "amount": 3707309693, "target": { "key": "bf1b59a6f7e408c3d7281769948afed7c58a0aaf673b7c297a682b86e4a97bb9" } } ], "extra": [ 1, 179, 70, 56, 201, 51, 221, 71, 242, 242, 217, 159, 171, 232, 52, 223, 236, 0, 157, 62, 93, 156, 179, 121, 226, 235, 214, 143, 229, 245, 245, 97, 147, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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