Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 628f6ec6773f21221950aaf72246e3098ad6439ece2c1ab8b7884bed3a0d6694

Tx prefix hash: 6023e829de32364e86c718148ef390ffdd7e8cf959ea0ba9a9192ac80290586d
Tx public key: f647a6cdd839a4da3b91e0c662cb03ef4383e51bd132ba237edc3b92582f503c
Timestamp: 1732780100 Timestamp [UCT]: 2024-11-28 07:48:20 Age [y:d:h:m:s]: 00:132:12:34:42
Block: 1163408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94516 RingCT/type: yes/0
Extra: 01f647a6cdd839a4da3b91e0c662cb03ef4383e51bd132ba237edc3b92582f503c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fce3fd7eafc025028f92b1d83d76ba7ae854c8d09dc2830d35dcb8f2fe66c228 0.600000000000 1649075 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": 1163418, "vin": [ { "gen": { "height": 1163408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fce3fd7eafc025028f92b1d83d76ba7ae854c8d09dc2830d35dcb8f2fe66c228" } } ], "extra": [ 1, 246, 71, 166, 205, 216, 57, 164, 218, 59, 145, 224, 198, 98, 203, 3, 239, 67, 131, 229, 27, 209, 50, 186, 35, 126, 220, 59, 146, 88, 47, 80, 60, 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