Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441d2293e53a058c382078da5117c84371d290647fe83aa2b3283de161053420

Tx prefix hash: a6dfb64bd709ac2459ae26f140b6040d2a510b6ef2d3ef9d3c6d64bf5eac60f6
Tx public key: b9df9e46c39c08c2f3ea523875e139354894a3e037b34321fed663c202ce7e1c
Timestamp: 1746059673 Timestamp [UCT]: 2025-05-01 00:34:33 Age [y:d:h:m:s]: 00:197:19:42:21
Block: 1273083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139096 RingCT/type: yes/0
Extra: 01b9df9e46c39c08c2f3ea523875e139354894a3e037b34321fed663c202ce7e1c02110000000b1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 665fd668f2d6e5455070c89a0bb50c8ac91d17dde4de117f698ac42d32ffeb59 0.600000000000 1760362 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": 1273093, "vin": [ { "gen": { "height": 1273083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "665fd668f2d6e5455070c89a0bb50c8ac91d17dde4de117f698ac42d32ffeb59" } } ], "extra": [ 1, 185, 223, 158, 70, 195, 156, 8, 194, 243, 234, 82, 56, 117, 225, 57, 53, 72, 148, 163, 224, 55, 179, 67, 33, 254, 214, 99, 194, 2, 206, 126, 28, 2, 17, 0, 0, 0, 11, 31, 144, 81, 122, 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