Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56362fecdcd76f95d301fcc0e564f14ed57dbb604b5603acbc7b4ae22629cebf

Tx prefix hash: 5fcb96b00563ed1b5abb1a30dad13c80b2b26f77a7d4c394517f7052ab5cde5d
Tx public key: bc8a779f1b4cf5115bc148c8855dc6015259c2bfebcdd7bb5a6223e73385581f
Timestamp: 1739281194 Timestamp [UCT]: 2025-02-11 13:39:54 Age [y:d:h:m:s]: 00:239:09:04:15
Block: 1216968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168780 RingCT/type: yes/0
Extra: 01bc8a779f1b4cf5115bc148c8855dc6015259c2bfebcdd7bb5a6223e73385581f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60a446dcc3b7c807a8e34d319dc9f4b7bdce276d884fa4c5806dfc539b0ddbdb 0.600000000000 1703777 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": 1216978, "vin": [ { "gen": { "height": 1216968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60a446dcc3b7c807a8e34d319dc9f4b7bdce276d884fa4c5806dfc539b0ddbdb" } } ], "extra": [ 1, 188, 138, 119, 159, 27, 76, 245, 17, 91, 193, 72, 200, 133, 93, 198, 1, 82, 89, 194, 191, 235, 205, 215, 187, 90, 98, 35, 231, 51, 133, 88, 31, 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