Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7d85451e7e22ce3eb4311b4aa29c91da7a599cde2c2244200f59acc96dc3c2

Tx prefix hash: 522198f3b9d97e8994b67ca401fa5a3affd3023dc93329c089e8fcffd45f1b35
Tx public key: dbf30c3847a8b58f2f578bfba7920310604076d613789a086f95707b83521e68
Timestamp: 1704697008 Timestamp [UCT]: 2024-01-08 06:56:48 Age [y:d:h:m:s]: 01:137:15:35:15
Block: 930666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359530 RingCT/type: yes/0
Extra: 01dbf30c3847a8b58f2f578bfba7920310604076d613789a086f95707b83521e680211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5adb5d54085de7c83bef5c9395754d457d971247aa6d8547872829d7011c193 0.600000000000 1388552 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": 930676, "vin": [ { "gen": { "height": 930666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5adb5d54085de7c83bef5c9395754d457d971247aa6d8547872829d7011c193" } } ], "extra": [ 1, 219, 243, 12, 56, 71, 168, 181, 143, 47, 87, 139, 251, 167, 146, 3, 16, 96, 64, 118, 214, 19, 120, 154, 8, 111, 149, 112, 123, 131, 82, 30, 104, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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