Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3edfdf1bb84ed2adb100aa6996518f9f43cf90fbc6d6bfb881339283273adc5

Tx prefix hash: a6394d7e2d271921eaefb451080e5dadd1f907b4eb1b3eb8ad3ddfab33ccf519
Tx public key: 4629fc34ca31f06c9b0007ca7f29b7ffb25c0a0c8f73ae7a302c19421a2b7672
Timestamp: 1713044970 Timestamp [UCT]: 2024-04-13 21:49:30 Age [y:d:h:m:s]: 01:020:14:19:27
Block: 999875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275699 RingCT/type: yes/0
Extra: 014629fc34ca31f06c9b0007ca7f29b7ffb25c0a0c8f73ae7a302c19421a2b767202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435b39fd90d5be21c9104d866f9c297428a9d1a67501f57d6aac1af1fa9c5f6c 0.600000000000 1460363 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": 999885, "vin": [ { "gen": { "height": 999875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435b39fd90d5be21c9104d866f9c297428a9d1a67501f57d6aac1af1fa9c5f6c" } } ], "extra": [ 1, 70, 41, 252, 52, 202, 49, 240, 108, 155, 0, 7, 202, 127, 41, 183, 255, 178, 92, 10, 12, 143, 115, 174, 122, 48, 44, 25, 66, 26, 43, 118, 114, 2, 17, 0, 0, 0, 2, 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