Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 790dc1c8dafd84d5183116576c2a25913d9f4fa953f2f62a326b97f7d92bdf60

Tx prefix hash: fb2e31ab2bcf3879d0c5bc46229c9d22843d669f492f1c56e0f2bb2781f45330
Tx public key: a631cc8e8ae56e3982ea700cad665aa33e54a45bdadca1bdc98c95e1a73e3a5b
Timestamp: 1737791902 Timestamp [UCT]: 2025-01-25 07:58:22 Age [y:d:h:m:s]: 00:142:15:14:22
Block: 1204861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101691 RingCT/type: yes/0
Extra: 01a631cc8e8ae56e3982ea700cad665aa33e54a45bdadca1bdc98c95e1a73e3a5b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4ff52b6ef5c63dc6e8d992fa8bfc0ccdd8a5286920ab889fbd280376c11fca4 0.600000000000 1691554 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": 1204871, "vin": [ { "gen": { "height": 1204861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4ff52b6ef5c63dc6e8d992fa8bfc0ccdd8a5286920ab889fbd280376c11fca4" } } ], "extra": [ 1, 166, 49, 204, 142, 138, 229, 110, 57, 130, 234, 112, 12, 173, 102, 90, 163, 62, 84, 164, 91, 218, 220, 161, 189, 201, 140, 149, 225, 167, 62, 58, 91, 2, 17, 0, 0, 0, 3, 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