Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970fb621b09a1066390dcab385f13f5fb781b47fa78d7fa525423b284448cd93

Tx prefix hash: e38572a5292167ebbeafd197fc7679669aec46504f2a022276b8c1798e173f39
Tx public key: 50a474329e3af3657a09bf228d184d596c8c8121ea26b984db2d3112f0c7132c
Timestamp: 1699372204 Timestamp [UCT]: 2023-11-07 15:50:04 Age [y:d:h:m:s]: 01:116:17:23:52
Block: 886543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344593 RingCT/type: yes/0
Extra: 0150a474329e3af3657a09bf228d184d596c8c8121ea26b984db2d3112f0c7132c02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.708785823000 dcy

stealth address amount amount idx
00: db7e0f93b759b04fbf669360b5e25a4508a33beb6ee3a8b198116e489b8ded64 0.708785823000 1342370 of 0

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": 886553, "vin": [ { "gen": { "height": 886543 } } ], "vout": [ { "amount": 708785823, "target": { "key": "db7e0f93b759b04fbf669360b5e25a4508a33beb6ee3a8b198116e489b8ded64" } } ], "extra": [ 1, 80, 164, 116, 50, 158, 58, 243, 101, 122, 9, 191, 34, 141, 24, 77, 89, 108, 140, 129, 33, 234, 38, 185, 132, 219, 45, 49, 18, 240, 199, 19, 44, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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