Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ef3b777a447bf028ad403fa305f8a961050ad0f4dfb2d626be4ee8c691cf25

Tx prefix hash: 6fac2536fa38de6f4bbd1ce002de602d1f5c7d1c38d234f4a584180daf344816
Tx public key: 36c92d3316d4155c206637db15425dcf62d8814d627a74e1c9f66625f55af82b
Timestamp: 1722073010 Timestamp [UCT]: 2024-07-27 09:36:50 Age [y:d:h:m:s]: 00:308:10:21:05
Block: 1074744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220386 RingCT/type: yes/0
Extra: 0136c92d3316d4155c206637db15425dcf62d8814d627a74e1c9f66625f55af82b021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0ebf18ddc864d31b5f430fa8710ee1d73ea4f088afc83bcb0cbc6e72b3e116e 0.600000000000 1547261 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": 1074754, "vin": [ { "gen": { "height": 1074744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0ebf18ddc864d31b5f430fa8710ee1d73ea4f088afc83bcb0cbc6e72b3e116e" } } ], "extra": [ 1, 54, 201, 45, 51, 22, 212, 21, 92, 32, 102, 55, 219, 21, 66, 93, 207, 98, 216, 129, 77, 98, 122, 116, 225, 201, 246, 102, 37, 245, 90, 248, 43, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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