Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b5f2a799b78f484dede954ad4cedb9b8ee3f99ea3bf7c963a9816145f4e9d05

Tx prefix hash: 784829ac0830c570557abbcdcc0b9e0ccb89d460c51cc59b38a606f8bff15541
Tx public key: 5eb8ff8feadb22bc7b42c86bdf02e84eba6c36e469f1e5a5d939cf2f1ac737a0
Timestamp: 1703139136 Timestamp [UCT]: 2023-12-21 06:12:16 Age [y:d:h:m:s]: 01:335:15:40:49
Block: 917789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498726 RingCT/type: yes/0
Extra: 015eb8ff8feadb22bc7b42c86bdf02e84eba6c36e469f1e5a5d939cf2f1ac737a002110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ad0e3a374408a9747000cea2b8b837d8b77078b6ffb904d151473814895d637 0.600000000000 1375371 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": 917799, "vin": [ { "gen": { "height": 917789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ad0e3a374408a9747000cea2b8b837d8b77078b6ffb904d151473814895d637" } } ], "extra": [ 1, 94, 184, 255, 143, 234, 219, 34, 188, 123, 66, 200, 107, 223, 2, 232, 78, 186, 108, 54, 228, 105, 241, 229, 165, 217, 57, 207, 47, 26, 199, 55, 160, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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