Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 327a83498ea63ff9a0844941f047b8f9b1079eeaa4d3e2f9b87df8ddaf2fbecd

Tx prefix hash: a92902721e58cbe79166ed5c1c8d6d043107d8725f7854aadd3a767c829817a4
Tx public key: efdc142b2df3cf349d1f4401882918c04579a35ec58959ead997e5417c9cb797
Timestamp: 1705481250 Timestamp [UCT]: 2024-01-17 08:47:30 Age [y:d:h:m:s]: 01:350:19:37:24
Block: 937171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509618 RingCT/type: yes/0
Extra: 01efdc142b2df3cf349d1f4401882918c04579a35ec58959ead997e5417c9cb79702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4666e674f8e40f8ea5568596fcdf7216003eae34f3dc4da1e5a5afdd353bf859 0.600000000000 1395215 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": 937181, "vin": [ { "gen": { "height": 937171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4666e674f8e40f8ea5568596fcdf7216003eae34f3dc4da1e5a5afdd353bf859" } } ], "extra": [ 1, 239, 220, 20, 43, 45, 243, 207, 52, 157, 31, 68, 1, 136, 41, 24, 192, 69, 121, 163, 94, 197, 137, 89, 234, 217, 151, 229, 65, 124, 156, 183, 151, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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