Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bf91760116d9ecc1014a025bb5f29a8f29cc4aa1b8b3ac69eba483d9cbc456f

Tx prefix hash: f98edfb91e7b073a596630db8ffbe32fcbb03dd7059bc73b8cac609be8fc8b8d
Tx public key: 79e9e21bd136a5944a61edfa5989a77d59643e5b4776b97f9329c1e5b43229d0
Timestamp: 1716269838 Timestamp [UCT]: 2024-05-21 05:37:18 Age [y:d:h:m:s]: 01:027:01:57:04
Block: 1026647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280154 RingCT/type: yes/0
Extra: 0179e9e21bd136a5944a61edfa5989a77d59643e5b4776b97f9329c1e5b43229d002110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 304e2025f5dd0abd4a4e811997cc1b43c38f5cc8c04092ce0f9063cebdc78d00 0.600000000000 1493840 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": 1026657, "vin": [ { "gen": { "height": 1026647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "304e2025f5dd0abd4a4e811997cc1b43c38f5cc8c04092ce0f9063cebdc78d00" } } ], "extra": [ 1, 121, 233, 226, 27, 209, 54, 165, 148, 74, 97, 237, 250, 89, 137, 167, 125, 89, 100, 62, 91, 71, 118, 185, 127, 147, 41, 193, 229, 180, 50, 41, 208, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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