Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a536accd0cde74c84e679ce3bda76e9cd43916a0195b69160ecbca013862eb4

Tx prefix hash: a4beb7674c50267c7feb9904f0f5867700108ec0a0e5420def6db9b28be96fc2
Tx public key: 35d2acf3e51fa9e1db5ebd0a4b1c39d8fc0f40f99c80b595eed226a49be95c5b
Timestamp: 1700859822 Timestamp [UCT]: 2023-11-24 21:03:42 Age [y:d:h:m:s]: 01:145:08:01:41
Block: 898878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365040 RingCT/type: yes/0
Extra: 0135d2acf3e51fa9e1db5ebd0a4b1c39d8fc0f40f99c80b595eed226a49be95c5b021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.645125233000 dcy

stealth address amount amount idx
00: 44f323b04b3d856644157f85ddbbc424c1b0b617a6bffd0dea55bd37b5ca4bd4 0.645125233000 1355315 of 0

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": 898888, "vin": [ { "gen": { "height": 898878 } } ], "vout": [ { "amount": 645125233, "target": { "key": "44f323b04b3d856644157f85ddbbc424c1b0b617a6bffd0dea55bd37b5ca4bd4" } } ], "extra": [ 1, 53, 210, 172, 243, 229, 31, 169, 225, 219, 94, 189, 10, 75, 28, 57, 216, 252, 15, 64, 249, 156, 128, 181, 149, 238, 210, 38, 164, 155, 233, 92, 91, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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