Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cadd57d71c685adc738a654d2c2ad1256b27388387caace01e366a887912982

Tx prefix hash: e03a038c46384d746dba9378acfb87204cdf9970e1e04907f39695327c39a6a9
Tx public key: 0f45e5f9ff3c2f7aa6bf1621e7b0ba9046cda329d13929dba55dc1f1ed4ec649
Timestamp: 1715230324 Timestamp [UCT]: 2024-05-09 04:52:04 Age [y:d:h:m:s]: 00:344:13:01:20
Block: 1018016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246287 RingCT/type: yes/0
Extra: 010f45e5f9ff3c2f7aa6bf1621e7b0ba9046cda329d13929dba55dc1f1ed4ec6490211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55f14d1b7018a08435e823501336925c7ec3b3a671510a84b6b907135662f70d 0.600000000000 1481801 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": 1018026, "vin": [ { "gen": { "height": 1018016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55f14d1b7018a08435e823501336925c7ec3b3a671510a84b6b907135662f70d" } } ], "extra": [ 1, 15, 69, 229, 249, 255, 60, 47, 122, 166, 191, 22, 33, 231, 176, 186, 144, 70, 205, 163, 41, 209, 57, 41, 219, 165, 93, 193, 241, 237, 78, 198, 73, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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