Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38a89af64683c06cb7a76bca6607c552974d1dd06f6af32978043c5245a0d88a

Tx prefix hash: f8ecd6b5004d50294c5b9c3a55461707be33bc1ddb03ff94c8797c8c5bf5b2e3
Tx public key: ca2903df3a1fddb9318638399e91a7e45d40409ce69f47ec3f9ea34ae5706316
Timestamp: 1722041873 Timestamp [UCT]: 2024-07-27 00:57:53 Age [y:d:h:m:s]: 00:319:03:39:00
Block: 1074479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228042 RingCT/type: yes/0
Extra: 01ca2903df3a1fddb9318638399e91a7e45d40409ce69f47ec3f9ea34ae5706316021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 515e46a2428da4e4e9e0560b230a0e632db50a2c3a307d3c9d100e9b1786f61f 0.600000000000 1546992 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": 1074489, "vin": [ { "gen": { "height": 1074479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "515e46a2428da4e4e9e0560b230a0e632db50a2c3a307d3c9d100e9b1786f61f" } } ], "extra": [ 1, 202, 41, 3, 223, 58, 31, 221, 185, 49, 134, 56, 57, 158, 145, 167, 228, 93, 64, 64, 156, 230, 159, 71, 236, 63, 158, 163, 74, 229, 112, 99, 22, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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