Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cf5d86fc246d2a61b8209e5757f15f8d16a9347bb1cdfeec0cb540ccf0f12e1

Tx prefix hash: 13a0eaba524ae71461a0dd61729e89458c1e032fb531c110b6aafc418c2edb0e
Tx public key: 0bef623d010f93be2ceb2a9959a1d2e95d363adb8e2877d13c877f1ca322c8a2
Timestamp: 1735989235 Timestamp [UCT]: 2025-01-04 11:13:55 Age [y:d:h:m:s]: 00:310:08:56:10
Block: 1189987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219321 RingCT/type: yes/0
Extra: 010bef623d010f93be2ceb2a9959a1d2e95d363adb8e2877d13c877f1ca322c8a20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef8bfbad30d665742f9f264f69dfb30c1c307a623aee24a4b7cfa89fae8ff0c0 0.600000000000 1676502 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": 1189997, "vin": [ { "gen": { "height": 1189987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef8bfbad30d665742f9f264f69dfb30c1c307a623aee24a4b7cfa89fae8ff0c0" } } ], "extra": [ 1, 11, 239, 98, 61, 1, 15, 147, 190, 44, 235, 42, 153, 89, 161, 210, 233, 93, 54, 58, 219, 142, 40, 119, 209, 60, 135, 127, 28, 163, 34, 200, 162, 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