Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cdae1d3801a9de03e255d4a46601dcd02e3162514328e4dc8de8bdb4566819e

Tx prefix hash: d2c9c1514c31dfc5ec23901ce922172bb435bdbdf745bd4e19e02ea867249da3
Tx public key: 8361e5b6e40128a95c9fe176ef893d066f11f1bf6fa6c5e88bad1641e4fe2432
Timestamp: 1737488488 Timestamp [UCT]: 2025-01-21 19:41:28 Age [y:d:h:m:s]: 00:148:04:09:42
Block: 1202345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105631 RingCT/type: yes/0
Extra: 018361e5b6e40128a95c9fe176ef893d066f11f1bf6fa6c5e88bad1641e4fe2432021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feed26def74ea3c358f45d22e29d3a6d4a4e5da988040ee3adb2ff43457ce3f7 0.600000000000 1689008 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": 1202355, "vin": [ { "gen": { "height": 1202345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feed26def74ea3c358f45d22e29d3a6d4a4e5da988040ee3adb2ff43457ce3f7" } } ], "extra": [ 1, 131, 97, 229, 182, 228, 1, 40, 169, 92, 159, 225, 118, 239, 137, 61, 6, 111, 17, 241, 191, 111, 166, 197, 232, 139, 173, 22, 65, 228, 254, 36, 50, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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