Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b815845420a4056d58e0048b4429e3f148415941b1f9f56e1e28e73817fc0d8e

Tx prefix hash: fb454fe8a625daab48f05337e80830e636a976f7d63d1ee1181619b53940c62e
Tx public key: bbfaf17e9c2d9d007d0b7c941e13fa1893d4952231a19ef9eb7e1637ecb7d506
Timestamp: 1702352282 Timestamp [UCT]: 2023-12-12 03:38:02 Age [y:d:h:m:s]: 01:074:01:28:45
Block: 911248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314027 RingCT/type: yes/0
Extra: 01bbfaf17e9c2d9d007d0b7c941e13fa1893d4952231a19ef9eb7e1637ecb7d506021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5949b437150686d039c89b9562de11f27e8cf1d7404b264591651209a2eae6a 0.600000000000 1368429 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": 911258, "vin": [ { "gen": { "height": 911248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5949b437150686d039c89b9562de11f27e8cf1d7404b264591651209a2eae6a" } } ], "extra": [ 1, 187, 250, 241, 126, 156, 45, 157, 0, 125, 11, 124, 148, 30, 19, 250, 24, 147, 212, 149, 34, 49, 161, 158, 249, 235, 126, 22, 55, 236, 183, 213, 6, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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