Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf13c162e83485c40fe239718bae9e3fb8c3e832946fb044cba8e1296b2df8a6

Tx prefix hash: d133c1a1019cda3869d16512165ea3ecca598339d74ebe9a4ea8e34a7336a31b
Tx public key: ad076d84d9ae63a53d536661350d686fff8671c14e97bea76152ac0d4f4c7542
Timestamp: 1734753180 Timestamp [UCT]: 2024-12-21 03:53:00 Age [y:d:h:m:s]: 00:015:02:24:48
Block: 1179777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10782 RingCT/type: yes/0
Extra: 01ad076d84d9ae63a53d536661350d686fff8671c14e97bea76152ac0d4f4c75420211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30ee46bc242ed58c63a54d8c95232ce6d9b7e3b654daafbc0a3db65f1bdeea87 0.600000000000 1666176 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": 1179787, "vin": [ { "gen": { "height": 1179777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30ee46bc242ed58c63a54d8c95232ce6d9b7e3b654daafbc0a3db65f1bdeea87" } } ], "extra": [ 1, 173, 7, 109, 132, 217, 174, 99, 165, 61, 83, 102, 97, 53, 13, 104, 111, 255, 134, 113, 193, 78, 151, 190, 167, 97, 82, 172, 13, 79, 76, 117, 66, 2, 17, 0, 0, 0, 2, 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