Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 757009ccdb3873bff6bf1c26b5d3cb32fdd0f8712f0027eb7d7898562bae189c

Tx prefix hash: 2c033705d065b4e49680de95e426ca410fccd7d274b535adfed8e430a69d241d
Tx public key: cb31d1f628ab9112b18d45f0c152063cd34526f9adbc2f71ca5a1151d72dca9d
Timestamp: 1710269361 Timestamp [UCT]: 2024-03-12 18:49:21 Age [y:d:h:m:s]: 01:051:17:46:35
Block: 976891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297984 RingCT/type: yes/0
Extra: 01cb31d1f628ab9112b18d45f0c152063cd34526f9adbc2f71ca5a1151d72dca9d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8103a2010eb74566d541d6d4cbc7f861140c74c63a1452929c2cf93018fe94b9 0.600000000000 1436890 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": 976901, "vin": [ { "gen": { "height": 976891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8103a2010eb74566d541d6d4cbc7f861140c74c63a1452929c2cf93018fe94b9" } } ], "extra": [ 1, 203, 49, 209, 246, 40, 171, 145, 18, 177, 141, 69, 240, 193, 82, 6, 60, 211, 69, 38, 249, 173, 188, 47, 113, 202, 90, 17, 81, 215, 45, 202, 157, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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