Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85e39f0982625fd25ffa657ccff31874bb0d1442d8d00d5706f3177637788379

Tx prefix hash: e0f012a9d856d0d5d091d95a7d2994745c991f337e57d3efa488b665158c766a
Tx public key: 56a3377ea824186b40d307fdbcab1afedd06a8c1e552af7558c67c55d6ea873a
Timestamp: 1740955581 Timestamp [UCT]: 2025-03-02 22:46:21 Age [y:d:h:m:s]: 00:262:23:40:59
Block: 1230827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185703 RingCT/type: yes/0
Extra: 0156a3377ea824186b40d307fdbcab1afedd06a8c1e552af7558c67c55d6ea873a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 328432a4cdbfd47a0d6998d649a4b10b9f0a60d8ebef2db6238d72d9f2a57737 0.600000000000 1717730 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": 1230837, "vin": [ { "gen": { "height": 1230827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "328432a4cdbfd47a0d6998d649a4b10b9f0a60d8ebef2db6238d72d9f2a57737" } } ], "extra": [ 1, 86, 163, 55, 126, 168, 36, 24, 107, 64, 211, 7, 253, 188, 171, 26, 254, 221, 6, 168, 193, 229, 82, 175, 117, 88, 198, 124, 85, 214, 234, 135, 58, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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