Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63c777e6d1833b627f149f25bb393374d18dce1f852aa3cdae37b924c18e99bf

Tx prefix hash: b0949019e602ab04700d6bfc9c1c57e06e8ad0a47406de8694cae1154ff73ee2
Tx public key: d5c5f8f05581574e614e45d0eda05679af47f6914b0d426a19bff77e63c4e19c
Timestamp: 1729325619 Timestamp [UCT]: 2024-10-19 08:13:39 Age [y:d:h:m:s]: 00:163:09:15:16
Block: 1134859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116550 RingCT/type: yes/0
Extra: 01d5c5f8f05581574e614e45d0eda05679af47f6914b0d426a19bff77e63c4e19c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bf2329976ee7551cc0dc3c3184cdcdfde2b0a4159d93947b4aa3d151be1d817 0.600000000000 1618186 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": 1134869, "vin": [ { "gen": { "height": 1134859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bf2329976ee7551cc0dc3c3184cdcdfde2b0a4159d93947b4aa3d151be1d817" } } ], "extra": [ 1, 213, 197, 248, 240, 85, 129, 87, 78, 97, 78, 69, 208, 237, 160, 86, 121, 175, 71, 246, 145, 75, 13, 66, 106, 25, 191, 247, 126, 99, 196, 225, 156, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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