Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d48fb4a5c51ad33acf37c880a7bb545f1d79019e5d9d1fc4ec8c96a7a8d058ce

Tx prefix hash: e0130c1e3a1a9ab19d05e9a69001359bb14b9bdca06506da9fd730870a875edf
Tx public key: 85b13b3279e9ca4cc95c38661c91728125d7ee4d94b698eb4c80f037a98e3a71
Timestamp: 1694784940 Timestamp [UCT]: 2023-09-15 13:35:40 Age [y:d:h:m:s]: 01:271:00:06:33
Block: 848698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454774 RingCT/type: yes/0
Extra: 0185b13b3279e9ca4cc95c38661c91728125d7ee4d94b698eb4c80f037a98e3a7102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.946043864000 dcy

stealth address amount amount idx
00: 05d9a940f5b9e59b4136b2f390275eb4eabfd05e31655828fe2402ff3c94c587 0.946043864000 1302320 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": 848708, "vin": [ { "gen": { "height": 848698 } } ], "vout": [ { "amount": 946043864, "target": { "key": "05d9a940f5b9e59b4136b2f390275eb4eabfd05e31655828fe2402ff3c94c587" } } ], "extra": [ 1, 133, 177, 59, 50, 121, 233, 202, 76, 201, 92, 56, 102, 28, 145, 114, 129, 37, 215, 238, 77, 148, 182, 152, 235, 76, 128, 240, 55, 169, 142, 58, 113, 2, 17, 0, 0, 0, 2, 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