Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63286241c9333fb15e9fc614af2688abab3f3bcbf762473337c913402c5d3e56

Tx prefix hash: 4d42fbcf0a07b106e26431f6d590b44974ca8cfe0a6991d25645dbdfd66ac8f7
Tx public key: 5639bcd4d42682f1eabda37a9613a2a5ef634b9c6b5b8c454eca6d549ec2f7ac
Timestamp: 1728787088 Timestamp [UCT]: 2024-10-13 02:38:08 Age [y:d:h:m:s]: 00:169:11:22:30
Block: 1130405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120903 RingCT/type: yes/0
Extra: 015639bcd4d42682f1eabda37a9613a2a5ef634b9c6b5b8c454eca6d549ec2f7ac02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23d4f133c52edf9371ef1e93ebf8269453c467c5a09aa57e888f65463b15f45a 0.600000000000 1613282 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": 1130415, "vin": [ { "gen": { "height": 1130405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23d4f133c52edf9371ef1e93ebf8269453c467c5a09aa57e888f65463b15f45a" } } ], "extra": [ 1, 86, 57, 188, 212, 212, 38, 130, 241, 234, 189, 163, 122, 150, 19, 162, 165, 239, 99, 75, 156, 107, 91, 140, 69, 78, 202, 109, 84, 158, 194, 247, 172, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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