Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bfe54dff38361aaaaa04f6e636e2d9d313c1d3bd34d2d22bbf9827def4c07d1

Tx prefix hash: 9e8e24c6983f88d5c5523c740087469705092824b03a171ac8094f9d4bc5d7e1
Tx public key: 6caf5b46faaee9e07564a17b4130b002404691985a03e5f394227eee61eb893d
Timestamp: 1711309063 Timestamp [UCT]: 2024-03-24 19:37:43 Age [y:d:h:m:s]: 01:063:23:04:51
Block: 985520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306705 RingCT/type: yes/0
Extra: 016caf5b46faaee9e07564a17b4130b002404691985a03e5f394227eee61eb893d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd44b21584257632d54ef2c73a95d07d2d5fd0d531a452d5c3efed8932a0b761 0.600000000000 1445733 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": 985530, "vin": [ { "gen": { "height": 985520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd44b21584257632d54ef2c73a95d07d2d5fd0d531a452d5c3efed8932a0b761" } } ], "extra": [ 1, 108, 175, 91, 70, 250, 174, 233, 224, 117, 100, 161, 123, 65, 48, 176, 2, 64, 70, 145, 152, 90, 3, 229, 243, 148, 34, 126, 238, 97, 235, 137, 61, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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