Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21ae0d1d4b3eaa4efee9ab96333e46db5dde8933523c32339090df46b01fd264

Tx prefix hash: b66b1fa2be99478806d512e2d36421df57ec46cfad4891a74cd61f3545c78851
Tx public key: fcd14929cb6f163c6dac4aeb3ad945cde93a336a217e43a123594468a739345f
Timestamp: 1723509390 Timestamp [UCT]: 2024-08-13 00:36:30 Age [y:d:h:m:s]: 00:216:11:33:47
Block: 1086647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154617 RingCT/type: yes/0
Extra: 01fcd14929cb6f163c6dac4aeb3ad945cde93a336a217e43a123594468a739345f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30e50b6b3b13babe2a8a9afba80c81eae480e46914ecc8b15fd2ad6877ef4b0f 0.600000000000 1561244 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": 1086657, "vin": [ { "gen": { "height": 1086647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30e50b6b3b13babe2a8a9afba80c81eae480e46914ecc8b15fd2ad6877ef4b0f" } } ], "extra": [ 1, 252, 209, 73, 41, 203, 111, 22, 60, 109, 172, 74, 235, 58, 217, 69, 205, 233, 58, 51, 106, 33, 126, 67, 161, 35, 89, 68, 104, 167, 57, 52, 95, 2, 17, 0, 0, 0, 4, 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