Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01b10032d3e50722c563f37cb484c9be973c066ec063e24def2c2a99f180454b

Tx prefix hash: 99e80275af8c3ed153e3c39d53365b14f286519d15f0ba03058153046780e6b7
Tx public key: 081c56e6e684ccce4e017e9794e0b2654fb5907ef2c22365ec3c7c9d982f96e2
Timestamp: 1732700005 Timestamp [UCT]: 2024-11-27 09:33:25 Age [y:d:h:m:s]: 00:132:20:27:59
Block: 1162752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94749 RingCT/type: yes/0
Extra: 01081c56e6e684ccce4e017e9794e0b2654fb5907ef2c22365ec3c7c9d982f96e20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b42fdd071fda93672e5d4f0b76704d4f02797472798539370657a1a91eb74866 0.600000000000 1648409 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": 1162762, "vin": [ { "gen": { "height": 1162752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b42fdd071fda93672e5d4f0b76704d4f02797472798539370657a1a91eb74866" } } ], "extra": [ 1, 8, 28, 86, 230, 230, 132, 204, 206, 78, 1, 126, 151, 148, 224, 178, 101, 79, 181, 144, 126, 242, 194, 35, 101, 236, 60, 124, 157, 152, 47, 150, 226, 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