Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 352f90a4cffd6e3b0cb447d748bef7d45583321e1f9c710112eeb3f690f3254e

Tx prefix hash: bcb6f14ea1d9684856cfdf54c33ffab35dd6efc9cc0e34aa4be31603d8e2c58c
Tx public key: a5c8fdc61e9fe262f5ffae828f7631b0560fd090dc33733fe008953e46a9d89d
Timestamp: 1711819282 Timestamp [UCT]: 2024-03-30 17:21:22 Age [y:d:h:m:s]: 01:075:12:01:03
Block: 989752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314869 RingCT/type: yes/0
Extra: 01a5c8fdc61e9fe262f5ffae828f7631b0560fd090dc33733fe008953e46a9d89d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd4d6b7982e2ed4410fc1dd56aa9e7ac266e688d80177bb9122429846d0d6b0a 0.600000000000 1450070 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": 989762, "vin": [ { "gen": { "height": 989752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd4d6b7982e2ed4410fc1dd56aa9e7ac266e688d80177bb9122429846d0d6b0a" } } ], "extra": [ 1, 165, 200, 253, 198, 30, 159, 226, 98, 245, 255, 174, 130, 143, 118, 49, 176, 86, 15, 208, 144, 220, 51, 115, 63, 224, 8, 149, 62, 70, 169, 216, 157, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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