Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b95e3ff748c525e9284544e862337e3da19adecd65e84ab38a7d4acf80fc7d03

Tx prefix hash: 901d72c34968ad4257b1f3a21d623aaafc5fdc37e1818e6b5ddd87e0d5a6f66c
Tx public key: 8a1c199af8461b65ee702cd54639a9d1e6bca439e73fd91bfc7d25f16aac3ab1
Timestamp: 1734889086 Timestamp [UCT]: 2024-12-22 17:38:06 Age [y:d:h:m:s]: 00:091:07:34:18
Block: 1180906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65001 RingCT/type: yes/0
Extra: 018a1c199af8461b65ee702cd54639a9d1e6bca439e73fd91bfc7d25f16aac3ab102110000000338edce2e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d44463547c9a8bd9b37d89c740edb05ed8026ccfd21a67dcdd54004d0b3341f3 0.600000000000 1667321 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": 1180916, "vin": [ { "gen": { "height": 1180906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d44463547c9a8bd9b37d89c740edb05ed8026ccfd21a67dcdd54004d0b3341f3" } } ], "extra": [ 1, 138, 28, 25, 154, 248, 70, 27, 101, 238, 112, 44, 213, 70, 57, 169, 209, 230, 188, 164, 57, 231, 63, 217, 27, 252, 125, 37, 241, 106, 172, 58, 177, 2, 17, 0, 0, 0, 3, 56, 237, 206, 46, 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