Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acdb51f3ea1a6e578b122afa458f0d4871663c391505b61be2a5aecf3e5c284f

Tx prefix hash: ce75a7d4e4d5dd61885506e7b26b22d5790708197af40e7734a2926072408ee9
Tx public key: e47ccc1b2aae2cb2da9286f1d73f3dc020401e2db8c6217bc7dccbef731db3e4
Timestamp: 1686387977 Timestamp [UCT]: 2023-06-10 09:06:17 Age [y:d:h:m:s]: 01:358:17:49:40
Block: 779149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517627 RingCT/type: yes/0
Extra: 01e47ccc1b2aae2cb2da9286f1d73f3dc020401e2db8c6217bc7dccbef731db3e402110000000175e3f0e9000000000000000000

1 output(s) for total of 1.608259344000 dcy

stealth address amount amount idx
00: 8def6235f2b80dd5a0eb099e42029e3241ab1124e2f19ec0ea6778322c4a9219 1.608259344000 1228794 of 0

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": 779159, "vin": [ { "gen": { "height": 779149 } } ], "vout": [ { "amount": 1608259344, "target": { "key": "8def6235f2b80dd5a0eb099e42029e3241ab1124e2f19ec0ea6778322c4a9219" } } ], "extra": [ 1, 228, 124, 204, 27, 42, 174, 44, 178, 218, 146, 134, 241, 215, 63, 61, 192, 32, 64, 30, 45, 184, 198, 33, 123, 199, 220, 203, 239, 115, 29, 179, 228, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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