Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f6f6357c4c483f7552c41b8484b1a72507fdde577f84f9fe284b4ca392ddab

Tx prefix hash: b89444953759641413d89cc86cfd36e0e68c66c3977f9d41fed1f0760ca336b2
Tx public key: d8949e1ff5d455c1148654b7ffe5138dca6fe226e8297b4a81d94040bf9b23fd
Timestamp: 1702377678 Timestamp [UCT]: 2023-12-12 10:41:18 Age [y:d:h:m:s]: 01:335:13:57:05
Block: 911474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498689 RingCT/type: yes/0
Extra: 01d8949e1ff5d455c1148654b7ffe5138dca6fe226e8297b4a81d94040bf9b23fd021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9bfa1ea1766d34d29a8ae6b4cd3fd73fc0034c35af13afe016719191dc0bcca 0.600000000000 1368678 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": 911484, "vin": [ { "gen": { "height": 911474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9bfa1ea1766d34d29a8ae6b4cd3fd73fc0034c35af13afe016719191dc0bcca" } } ], "extra": [ 1, 216, 148, 158, 31, 245, 212, 85, 193, 20, 134, 84, 183, 255, 229, 19, 141, 202, 111, 226, 38, 232, 41, 123, 74, 129, 217, 64, 64, 191, 155, 35, 253, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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