Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1553d1bdc5d63cc5bbe40d5805cdcfe28c0541275bf52458bbf31b80e7e8e09a

Tx prefix hash: abf6ecb3c78ae3c60187d804509062f45e73ea42656dd928e16d30510474031e
Tx public key: 26a57b3a54eff8baff212fe40beff8e1f0f8c3d3abd9b55f823135b35dd17949
Timestamp: 1705588076 Timestamp [UCT]: 2024-01-18 14:27:56 Age [y:d:h:m:s]: 01:127:08:00:18
Block: 938060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352135 RingCT/type: yes/0
Extra: 0126a57b3a54eff8baff212fe40beff8e1f0f8c3d3abd9b55f823135b35dd1794902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcb83e020a535afd7e8753c90031d8483960f4f7f272244011e20b7fc5b4e6c3 0.600000000000 1396124 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": 938070, "vin": [ { "gen": { "height": 938060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcb83e020a535afd7e8753c90031d8483960f4f7f272244011e20b7fc5b4e6c3" } } ], "extra": [ 1, 38, 165, 123, 58, 84, 239, 248, 186, 255, 33, 47, 228, 11, 239, 248, 225, 240, 248, 195, 211, 171, 217, 181, 95, 130, 49, 53, 179, 93, 209, 121, 73, 2, 17, 0, 0, 0, 3, 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