Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 283fc4aca42a3b598b87301640eb168911f8018c41e8214c1d18cafb068d51d6

Tx prefix hash: fd6a41342513fd9e064306a4bee55b89308a776d96150efca16704d4027357eb
Tx public key: 2754bda0f1e79e2c2791dc7a89eaf2089ee778b6fbeddbf2eb859a6a417757fd
Timestamp: 1726504761 Timestamp [UCT]: 2024-09-16 16:39:21 Age [y:d:h:m:s]: 00:115:20:48:59
Block: 1111477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82860 RingCT/type: yes/0
Extra: 012754bda0f1e79e2c2791dc7a89eaf2089ee778b6fbeddbf2eb859a6a417757fd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc53f77b34f1d1fe7d236f363046dc18b9bbc4fa7495855d4ffe8174a0022dec 0.600000000000 1590452 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": 1111487, "vin": [ { "gen": { "height": 1111477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc53f77b34f1d1fe7d236f363046dc18b9bbc4fa7495855d4ffe8174a0022dec" } } ], "extra": [ 1, 39, 84, 189, 160, 241, 231, 158, 44, 39, 145, 220, 122, 137, 234, 242, 8, 158, 231, 120, 182, 251, 237, 219, 242, 235, 133, 154, 106, 65, 119, 87, 253, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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