Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dd23564da9cc4dfc36a06b7884f87ad5f99a597abc6ad8564584a90a5a4717b

Tx prefix hash: 0e15bee2738b8403b951fa3202bbb5db7dc838e6383d664780b7c5e8db90c629
Tx public key: ea8edb92412a54d2fa6bd43195e49f2b1e8680a1ea3719175cc7dc8963eafde8
Timestamp: 1735559471 Timestamp [UCT]: 2024-12-30 11:51:11 Age [y:d:h:m:s]: 00:352:04:25:00
Block: 1186416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249268 RingCT/type: yes/0
Extra: 01ea8edb92412a54d2fa6bd43195e49f2b1e8680a1ea3719175cc7dc8963eafde80211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a99cd808f13106949dbd395275e76888d840144adb307b6f0cc8a2ac82759578 0.600000000000 1672897 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": 1186426, "vin": [ { "gen": { "height": 1186416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a99cd808f13106949dbd395275e76888d840144adb307b6f0cc8a2ac82759578" } } ], "extra": [ 1, 234, 142, 219, 146, 65, 42, 84, 210, 250, 107, 212, 49, 149, 228, 159, 43, 30, 134, 128, 161, 234, 55, 25, 23, 92, 199, 220, 137, 99, 234, 253, 232, 2, 17, 0, 0, 0, 8, 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