Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2908c2809095d154c47700d1faaa54f6c1b1f1e6252634993f82667ecd87c58d

Tx prefix hash: 98f007aafdbe34f4e8513cb485c8e902c59fcf2d524f2bf80443fdf3ea416f7f
Tx public key: 074bec038f07a5e80dadfe84a6eea68026d64fd3c2950bcfe7d81ce448bf6b59
Timestamp: 1714974676 Timestamp [UCT]: 2024-05-06 05:51:16 Age [y:d:h:m:s]: 01:002:05:24:52
Block: 1015894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262520 RingCT/type: yes/0
Extra: 01074bec038f07a5e80dadfe84a6eea68026d64fd3c2950bcfe7d81ce448bf6b590211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea1a0777c1cfb5b033790c705c7c452aaf3fdcb59945dd22bbda67eeeb277e6f 0.600000000000 1479337 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": 1015904, "vin": [ { "gen": { "height": 1015894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea1a0777c1cfb5b033790c705c7c452aaf3fdcb59945dd22bbda67eeeb277e6f" } } ], "extra": [ 1, 7, 75, 236, 3, 143, 7, 165, 232, 13, 173, 254, 132, 166, 238, 166, 128, 38, 214, 79, 211, 194, 149, 11, 207, 231, 216, 28, 228, 72, 191, 107, 89, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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