Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f5848097df43b9fa5f99f5207101760c6c68c0588d24a5888d7fb0a47e31fcd

Tx prefix hash: 51db868f42f95cb1c49044253ef2888d9ccfcd6a4ad4c2ccab89dd4e0b8c0318
Tx public key: 0bdfa8852dcdb09576292f32b72a19881ef26d672079a9174f0d41229cb4d099
Timestamp: 1738304574 Timestamp [UCT]: 2025-01-31 06:22:54 Age [y:d:h:m:s]: 00:040:20:37:31
Block: 1208895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29227 RingCT/type: yes/0
Extra: 010bdfa8852dcdb09576292f32b72a19881ef26d672079a9174f0d41229cb4d099021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd10067180bc144d312c8b8d64f40b39d55408916e22b66cb6b1a12e4a4b2e5 0.600000000000 1695630 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": 1208905, "vin": [ { "gen": { "height": 1208895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd10067180bc144d312c8b8d64f40b39d55408916e22b66cb6b1a12e4a4b2e5" } } ], "extra": [ 1, 11, 223, 168, 133, 45, 205, 176, 149, 118, 41, 47, 50, 183, 42, 25, 136, 30, 242, 109, 103, 32, 121, 169, 23, 79, 13, 65, 34, 156, 180, 208, 153, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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