Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49352e64b11e09c5650180eae46d02a985402d4ad9f1bb593fae7f8f4919cb03

Tx prefix hash: 8f20b7c5c873d043560c5382226ee990347abdb7815effef1b5679d933400a3c
Tx public key: 31d1be1bcf016e5ac76c612ee7f16fa3a35500b2ef64318e2ab030891240d233
Timestamp: 1711422322 Timestamp [UCT]: 2024-03-26 03:05:22 Age [y:d:h:m:s]: 01:012:14:20:23
Block: 986467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269937 RingCT/type: yes/0
Extra: 0131d1be1bcf016e5ac76c612ee7f16fa3a35500b2ef64318e2ab030891240d233021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fce9c5fa106c69a116d5ba69fae02fe7b3e30f7ff5bd1f66777d4b5ed579493e 0.600000000000 1446696 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": 986477, "vin": [ { "gen": { "height": 986467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fce9c5fa106c69a116d5ba69fae02fe7b3e30f7ff5bd1f66777d4b5ed579493e" } } ], "extra": [ 1, 49, 209, 190, 27, 207, 1, 110, 90, 199, 108, 97, 46, 231, 241, 111, 163, 163, 85, 0, 178, 239, 100, 49, 142, 42, 176, 48, 137, 18, 64, 210, 51, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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