Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd2860e6bbb911b4c35b8896ea453eb59ec981b4e22477a04ec6f638d5bbc45

Tx prefix hash: 31313d3dddab4489dcd3e70e68921818bb299f543ca34343133f802397e4cade
Tx public key: fbf70705ebe8d6c68a86b14af5cf25011eeb4aeb0823f2b0a26dffaa35e03bcc
Timestamp: 1733223845 Timestamp [UCT]: 2024-12-03 11:04:05 Age [y:d:h:m:s]: 00:106:10:50:50
Block: 1167081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75903 RingCT/type: yes/0
Extra: 01fbf70705ebe8d6c68a86b14af5cf25011eeb4aeb0823f2b0a26dffaa35e03bcc021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 058eb817f8e5b0ca918fa6c2fcd069961b29df56c859251bcae5da33f1c7c66a 0.600000000000 1652774 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": 1167091, "vin": [ { "gen": { "height": 1167081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "058eb817f8e5b0ca918fa6c2fcd069961b29df56c859251bcae5da33f1c7c66a" } } ], "extra": [ 1, 251, 247, 7, 5, 235, 232, 214, 198, 138, 134, 177, 74, 245, 207, 37, 1, 30, 235, 74, 235, 8, 35, 242, 176, 162, 109, 255, 170, 53, 224, 59, 204, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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