Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bc62444b61f7c6d1c0b464a3b49b8d3b372897237a84ccf4c577d248743a810

Tx prefix hash: 41ea41363d2d5665daf8840bf0e1b4587a741cebaf62f11ce972b00f04150e5c
Tx public key: 08a7bd765004dbab4fc7d67061a4b141508b20037b6b1c775360f04d948b02ef
Timestamp: 1723137376 Timestamp [UCT]: 2024-08-08 17:16:16 Age [y:d:h:m:s]: 00:200:06:10:13
Block: 1083561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142982 RingCT/type: yes/0
Extra: 0108a7bd765004dbab4fc7d67061a4b141508b20037b6b1c775360f04d948b02ef021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e285ba294348f3e638a34ef3160a06f513fa3b3817ee7c78a0fe34e4fd2d4431 0.600000000000 1557528 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": 1083571, "vin": [ { "gen": { "height": 1083561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e285ba294348f3e638a34ef3160a06f513fa3b3817ee7c78a0fe34e4fd2d4431" } } ], "extra": [ 1, 8, 167, 189, 118, 80, 4, 219, 171, 79, 199, 214, 112, 97, 164, 177, 65, 80, 139, 32, 3, 123, 107, 28, 119, 83, 96, 240, 77, 148, 139, 2, 239, 2, 17, 0, 0, 0, 3, 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