Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7db2e29209747aa4d632a4457a6d7e340d441061e39b97d7b8acdfe7fed89af6

Tx prefix hash: 36a2fee5a7ac34f38eabe5a2fb0b8725b6dc9582c34ae20138688450b7522320
Tx public key: 57ea3a95313c1676d10971f85948503c183be87563cf9e658a4b9cc61551d916
Timestamp: 1715222987 Timestamp [UCT]: 2024-05-09 02:49:47 Age [y:d:h:m:s]: 00:249:01:02:10
Block: 1017957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178246 RingCT/type: yes/0
Extra: 0157ea3a95313c1676d10971f85948503c183be87563cf9e658a4b9cc61551d9160211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 811b0c25d28968877dc7ebfbd7c0ac9aedc8dac2331cc0df2b3395e5eb56a2f5 0.600000000000 1481742 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": 1017967, "vin": [ { "gen": { "height": 1017957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "811b0c25d28968877dc7ebfbd7c0ac9aedc8dac2331cc0df2b3395e5eb56a2f5" } } ], "extra": [ 1, 87, 234, 58, 149, 49, 60, 22, 118, 209, 9, 113, 248, 89, 72, 80, 60, 24, 59, 232, 117, 99, 207, 158, 101, 138, 75, 156, 198, 21, 81, 217, 22, 2, 17, 0, 0, 0, 3, 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