Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 626bcd357323317a25807b7def5f329a0f20b9b75a28f5be12c69bccccd34ac3

Tx prefix hash: 1fdc9e762ac20d5ab00686a555490c27622f8ff45d86717b9fa2fcc9a1d47d4f
Tx public key: b3690574c09399f2ffe0316e0e4b3678f86db7da0ba6e7fe7dda64e0a317b434
Timestamp: 1725096722 Timestamp [UCT]: 2024-08-31 09:32:02 Age [y:d:h:m:s]: 00:237:13:25:59
Block: 1099811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169629 RingCT/type: yes/0
Extra: 01b3690574c09399f2ffe0316e0e4b3678f86db7da0ba6e7fe7dda64e0a317b43402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 602a836f4b5236d3d72db22779baf736f6f0997ebaca50be670b830c2b978dca 0.600000000000 1575780 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": 1099821, "vin": [ { "gen": { "height": 1099811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "602a836f4b5236d3d72db22779baf736f6f0997ebaca50be670b830c2b978dca" } } ], "extra": [ 1, 179, 105, 5, 116, 192, 147, 153, 242, 255, 224, 49, 110, 14, 75, 54, 120, 248, 109, 183, 218, 11, 166, 231, 254, 125, 218, 100, 224, 163, 23, 180, 52, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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