Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04276bf0092d3fea81d2ff98a3a8689074c9d32ca4677684d531ddc4b2bc8cf1

Tx prefix hash: cf39bb02cb55d62526bfe03f46a5ddf0c7174761482ffa4e7cf5baa7299b9868
Tx public key: 0e4c07457a4c0a322a6e7b316aaeb7dccb33078ca8ce41ce6ffbadb4f2b436c1
Timestamp: 1704796648 Timestamp [UCT]: 2024-01-09 10:37:28 Age [y:d:h:m:s]: 01:328:19:02:12
Block: 931498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493846 RingCT/type: yes/0
Extra: 010e4c07457a4c0a322a6e7b316aaeb7dccb33078ca8ce41ce6ffbadb4f2b436c10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b3e2a12839e29752a6c5e77a62738c047414af749b521ea62f227955f0af017 0.600000000000 1389400 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": 931508, "vin": [ { "gen": { "height": 931498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b3e2a12839e29752a6c5e77a62738c047414af749b521ea62f227955f0af017" } } ], "extra": [ 1, 14, 76, 7, 69, 122, 76, 10, 50, 42, 110, 123, 49, 106, 174, 183, 220, 203, 51, 7, 140, 168, 206, 65, 206, 111, 251, 173, 180, 242, 180, 54, 193, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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