Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31128876a85adfd4bb9b14b5e6f0583a7ab31e60ea90bd882318cff389b424a5

Tx prefix hash: 8a2d612f8a22cd89600f14af57db208ba4b81fd4238ffb32fad57401b2768fd2
Tx public key: cf52f7cd0f65f4339591bde7c6918cb85ce5e2fcc968cb99ff139b836b820a08
Timestamp: 1714288510 Timestamp [UCT]: 2024-04-28 07:15:10 Age [y:d:h:m:s]: 00:200:01:51:03
Block: 1010204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143221 RingCT/type: yes/0
Extra: 01cf52f7cd0f65f4339591bde7c6918cb85ce5e2fcc968cb99ff139b836b820a0802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0318d3b67efdf8ab88452601028a95b41f9af4eec27ecec0c6ce374e0ee4de55 0.600000000000 1472088 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": 1010214, "vin": [ { "gen": { "height": 1010204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0318d3b67efdf8ab88452601028a95b41f9af4eec27ecec0c6ce374e0ee4de55" } } ], "extra": [ 1, 207, 82, 247, 205, 15, 101, 244, 51, 149, 145, 189, 231, 198, 145, 140, 184, 92, 229, 226, 252, 201, 104, 203, 153, 255, 19, 155, 131, 107, 130, 10, 8, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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