Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 374b4437dd6ebac6b33d70a3107a10a41834cec4e0c152e8c92bb8e1ca4fb4b9

Tx prefix hash: e82988169c5387cba83da81fdc1147ef1ca876a35d71b028f4d513f526236811
Tx public key: 02bac22206953048f475edef1b84f385abfc6f6d9de7e2c9100d2b2f08203238
Timestamp: 1732687510 Timestamp [UCT]: 2024-11-27 06:05:10 Age [y:d:h:m:s]: 00:136:14:57:58
Block: 1162644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97452 RingCT/type: yes/0
Extra: 0102bac22206953048f475edef1b84f385abfc6f6d9de7e2c9100d2b2f082032380211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be940d1e3e9b3fbefa6905834a3b7ee3450a02c55710443154e1210c816f755f 0.600000000000 1648301 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": 1162654, "vin": [ { "gen": { "height": 1162644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be940d1e3e9b3fbefa6905834a3b7ee3450a02c55710443154e1210c816f755f" } } ], "extra": [ 1, 2, 186, 194, 34, 6, 149, 48, 72, 244, 117, 237, 239, 27, 132, 243, 133, 171, 252, 111, 109, 157, 231, 226, 201, 16, 13, 43, 47, 8, 32, 50, 56, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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