Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6bf40490f9dfecb8f710c96db4d72b570f2b43805dbd4b0aa4dda60ed8c656c

Tx prefix hash: f79b278abc32ff411e4a656fcefb0defb57febef8766886f70acab62855ccc18
Tx public key: e999bf9e4d041ab67bb10ec3ec5e07e66b32525ddd71c542cb17ca8c4f1bc4cc
Timestamp: 1736932431 Timestamp [UCT]: 2025-01-15 09:13:51 Age [y:d:h:m:s]: 00:336:06:23:40
Block: 1197782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237885 RingCT/type: yes/0
Extra: 01e999bf9e4d041ab67bb10ec3ec5e07e66b32525ddd71c542cb17ca8c4f1bc4cc0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b7f59f5903ffa9db193e32969a65563d6a4c981ec6955d32e111cfe9f74cfc2 0.600000000000 1684399 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": 1197792, "vin": [ { "gen": { "height": 1197782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b7f59f5903ffa9db193e32969a65563d6a4c981ec6955d32e111cfe9f74cfc2" } } ], "extra": [ 1, 233, 153, 191, 158, 77, 4, 26, 182, 123, 177, 14, 195, 236, 94, 7, 230, 107, 50, 82, 93, 221, 113, 197, 66, 203, 23, 202, 140, 79, 27, 196, 204, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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