Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462bda57662aea1471119a8ab5d46204708c468844a0e94be12a4ab629af0eed

Tx prefix hash: 88a3c1ae5fdc4e97859d90595ec1fbc687aafb602f27daa9da7fa49a476ba642
Tx public key: fc3c2aa9d55f207aa11a26b730730c8a38d6a3051e6e3163d1f9d74838e2eae6
Timestamp: 1705642932 Timestamp [UCT]: 2024-01-19 05:42:12 Age [y:d:h:m:s]: 00:358:01:16:38
Block: 938509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256356 RingCT/type: yes/0
Extra: 01fc3c2aa9d55f207aa11a26b730730c8a38d6a3051e6e3163d1f9d74838e2eae602110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c69569b3832497ba65cb6fd909c9e2cf3300fc1abb944acd5b2b87e4bbd430c3 0.600000000000 1396579 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": 938519, "vin": [ { "gen": { "height": 938509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c69569b3832497ba65cb6fd909c9e2cf3300fc1abb944acd5b2b87e4bbd430c3" } } ], "extra": [ 1, 252, 60, 42, 169, 213, 95, 32, 122, 161, 26, 38, 183, 48, 115, 12, 138, 56, 214, 163, 5, 30, 110, 49, 99, 209, 249, 215, 72, 56, 226, 234, 230, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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