Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 330646cd40d09407e949f776fc78c30497ca1e899426eb47daf504dc226be1c2

Tx prefix hash: 3d7472fae36f2552241ffa5811a0ac5d69e7c2f6ea036b218aef5700c1e2fdea
Tx public key: 20055138f019557c2b51e954c92e732e99dc36b2c04d4151fa19e86d9e9142f0
Timestamp: 1736099276 Timestamp [UCT]: 2025-01-05 17:47:56 Age [y:d:h:m:s]: 00:317:07:09:48
Block: 1190893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224292 RingCT/type: yes/0
Extra: 0120055138f019557c2b51e954c92e732e99dc36b2c04d4151fa19e86d9e9142f002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 457a514fd4e3785df05b734615ab99fad139df5df13c787dd06d2c2a286282af 0.600000000000 1677416 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": 1190903, "vin": [ { "gen": { "height": 1190893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "457a514fd4e3785df05b734615ab99fad139df5df13c787dd06d2c2a286282af" } } ], "extra": [ 1, 32, 5, 81, 56, 240, 25, 85, 124, 43, 81, 233, 84, 201, 46, 115, 46, 153, 220, 54, 178, 192, 77, 65, 81, 250, 25, 232, 109, 158, 145, 66, 240, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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