Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: decc73501252aa8bf44166b244433d4688fefea228ffd2c7f83229242b5b7dd8

Tx prefix hash: 3c98aff8bbe656c7427995688f215369a0d70445353c79b45dadf2271f5d029c
Tx public key: a8254a94bbd5e95c06e07622ad0b852f764fb5441f7f44e89f9a8de47ce098db
Timestamp: 1708330917 Timestamp [UCT]: 2024-02-19 08:21:57 Age [y:d:h:m:s]: 01:121:09:30:50
Block: 960811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347706 RingCT/type: yes/0
Extra: 01a8254a94bbd5e95c06e07622ad0b852f764fb5441f7f44e89f9a8de47ce098db021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd14964282586751f8b6fd2cb2b53fa1a4af8cce08343b8d725a6319afeee2f5 0.600000000000 1420398 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": 960821, "vin": [ { "gen": { "height": 960811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd14964282586751f8b6fd2cb2b53fa1a4af8cce08343b8d725a6319afeee2f5" } } ], "extra": [ 1, 168, 37, 74, 148, 187, 213, 233, 92, 6, 224, 118, 34, 173, 11, 133, 47, 118, 79, 181, 68, 31, 127, 68, 232, 159, 154, 141, 228, 124, 224, 152, 219, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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