Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b36db24ccfdd64c81d9235f9351bc03ba63cedce288d4059c805f6f92e25b9

Tx prefix hash: 6b9e5813b4ac8261ee8b0dd906cef092d8356906a3389581711c6f37f9ef581c
Tx public key: 19fb63e5576cb93a78db1e88c3637cf58cba7ec420c364a0c4b41200a3ec2848
Timestamp: 1714410341 Timestamp [UCT]: 2024-04-29 17:05:41 Age [y:d:h:m:s]: 00:270:07:53:18
Block: 1011210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193452 RingCT/type: yes/0
Extra: 0119fb63e5576cb93a78db1e88c3637cf58cba7ec420c364a0c4b41200a3ec284802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c6651c31befaa79385a5b5cb108b0fb686ab2f3ce45a407bf6ac5c80df2cbd0 0.600000000000 1473382 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": 1011220, "vin": [ { "gen": { "height": 1011210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c6651c31befaa79385a5b5cb108b0fb686ab2f3ce45a407bf6ac5c80df2cbd0" } } ], "extra": [ 1, 25, 251, 99, 229, 87, 108, 185, 58, 120, 219, 30, 136, 195, 99, 124, 245, 140, 186, 126, 196, 32, 195, 100, 160, 196, 180, 18, 0, 163, 236, 40, 72, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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