Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0993b7a2e8642a7354a281079aeac4232c94b75674fa0856d82101f225b6a065

Tx prefix hash: 2b3d1fe6016970f8106db377479f053da40b2b32f17db923baf2fdfe636198b6
Tx public key: f591abcb51825a061fb643e50c7bd2b843cec45d44efbfe5248761ff0cfd9606
Timestamp: 1720909991 Timestamp [UCT]: 2024-07-13 22:33:11 Age [y:d:h:m:s]: 00:320:01:14:03
Block: 1065108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228707 RingCT/type: yes/0
Extra: 01f591abcb51825a061fb643e50c7bd2b843cec45d44efbfe5248761ff0cfd960602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e143bae7a3b4ad2cecd10c6c9910c79080e9bb6490f066d7d3037074213d5ce 0.600000000000 1535651 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": 1065118, "vin": [ { "gen": { "height": 1065108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e143bae7a3b4ad2cecd10c6c9910c79080e9bb6490f066d7d3037074213d5ce" } } ], "extra": [ 1, 245, 145, 171, 203, 81, 130, 90, 6, 31, 182, 67, 229, 12, 123, 210, 184, 67, 206, 196, 93, 68, 239, 191, 229, 36, 135, 97, 255, 12, 253, 150, 6, 2, 17, 0, 0, 0, 6, 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