Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a3f8f0f7d46b5481aeca4431f8ef710c2e2444b992b8cad344a7c1431236305

Tx prefix hash: f0d0c9b71b4563bd4ab445753c7ee82608418c398d1089b82215595d2f3b70fe
Tx public key: ba91d8877019f7db5cf69a93c317f4bb63963282a6d67f573fff2bbcee8525b1
Timestamp: 1711075308 Timestamp [UCT]: 2024-03-22 02:41:48 Age [y:d:h:m:s]: 01:084:14:06:11
Block: 983583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321379 RingCT/type: yes/0
Extra: 01ba91d8877019f7db5cf69a93c317f4bb63963282a6d67f573fff2bbcee8525b102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d6ff99e18eb8dc2361d238098af934b22f36faf0a6c4024d7c16aaf33fd7f23 0.600000000000 1443724 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": 983593, "vin": [ { "gen": { "height": 983583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d6ff99e18eb8dc2361d238098af934b22f36faf0a6c4024d7c16aaf33fd7f23" } } ], "extra": [ 1, 186, 145, 216, 135, 112, 25, 247, 219, 92, 246, 154, 147, 195, 23, 244, 187, 99, 150, 50, 130, 166, 214, 127, 87, 63, 255, 43, 188, 238, 133, 37, 177, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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