Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01bfc5c6178f35ac1d8bf2a6b094724e065d6a22dcc1c320ddefd43469a924d3

Tx prefix hash: 97f6b0387180161728bffb7a22819ec9ce0f9670eb150220097559c342d66f1c
Tx public key: b24fa0b9a3ac26f85eeadf86fdba7eda3a9fbab5d793e8542759e09a22f7b695
Timestamp: 1697118387 Timestamp [UCT]: 2023-10-12 13:46:27 Age [y:d:h:m:s]: 01:138:20:10:40
Block: 868076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360214 RingCT/type: yes/0
Extra: 01b24fa0b9a3ac26f85eeadf86fdba7eda3a9fbab5d793e8542759e09a22f7b69502110000000333af99f4000000000000000000

1 output(s) for total of 0.816025794000 dcy

stealth address amount amount idx
00: 483dfdbd2c94c74eb0bc5cb900ccf6633474c6b0011813ae227f27445516620b 0.816025794000 1322837 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": 868086, "vin": [ { "gen": { "height": 868076 } } ], "vout": [ { "amount": 816025794, "target": { "key": "483dfdbd2c94c74eb0bc5cb900ccf6633474c6b0011813ae227f27445516620b" } } ], "extra": [ 1, 178, 79, 160, 185, 163, 172, 38, 248, 94, 234, 223, 134, 253, 186, 126, 218, 58, 159, 186, 181, 215, 147, 232, 84, 39, 89, 224, 154, 34, 247, 182, 149, 2, 17, 0, 0, 0, 3, 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