Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 811c2aa2982303d86f866e297f72a56d4426b7b20f1dea8ed299fc7e0b380163

Tx prefix hash: bb75e70429406cb19865af5b00e423b69806573ba247b457b2051439a6649639
Tx public key: 2732b227e8efb8ae7dcc19f5801e7b3ab53bb73beaa39d9106c4167d16428314
Timestamp: 1731997413 Timestamp [UCT]: 2024-11-19 06:23:33 Age [y:d:h:m:s]: 00:136:00:16:20
Block: 1156929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97022 RingCT/type: yes/0
Extra: 012732b227e8efb8ae7dcc19f5801e7b3ab53bb73beaa39d9106c4167d164283140211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61c10c537b00b45fc13a8df4bf13f1b75b8f4600bd368f051c6f491b26a196cb 0.600000000000 1642552 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": 1156939, "vin": [ { "gen": { "height": 1156929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61c10c537b00b45fc13a8df4bf13f1b75b8f4600bd368f051c6f491b26a196cb" } } ], "extra": [ 1, 39, 50, 178, 39, 232, 239, 184, 174, 125, 204, 25, 245, 128, 30, 123, 58, 181, 59, 183, 59, 234, 163, 157, 145, 6, 196, 22, 125, 22, 66, 131, 20, 2, 17, 0, 0, 0, 3, 31, 10, 83, 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