Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0138c3575f72b90c40667f3c83fb75f53c354956603265099726148238effa6

Tx prefix hash: b57ec1d4ce913c40fdf771bebc6578869204b9323f1b0f62446f4e44730f082c
Tx public key: 1eef0894ad1fb5c26c3ead99d3c338a94b21c913bfef1f54fdf348743b7f3ab0
Timestamp: 1724611568 Timestamp [UCT]: 2024-08-25 18:46:08 Age [y:d:h:m:s]: 00:276:09:29:06
Block: 1095792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197442 RingCT/type: yes/0
Extra: 011eef0894ad1fb5c26c3ead99d3c338a94b21c913bfef1f54fdf348743b7f3ab002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5155145dc861b6b666260d491a587ac52d8494890bfcab86fd1f329f6d56983 0.600000000000 1570975 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": 1095802, "vin": [ { "gen": { "height": 1095792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5155145dc861b6b666260d491a587ac52d8494890bfcab86fd1f329f6d56983" } } ], "extra": [ 1, 30, 239, 8, 148, 173, 31, 181, 194, 108, 62, 173, 153, 211, 195, 56, 169, 75, 33, 201, 19, 191, 239, 31, 84, 253, 243, 72, 116, 59, 127, 58, 176, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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