Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fbd1a4d29cf77f27979c93238948d9480cab81413e4b4761e2fa8a8603d73dc

Tx prefix hash: e14d16581b0a51d4e52ce7b77db0c63766a9c43444709f238629519282734912
Tx public key: 8fb012aa909eff0ab78b755fb2d6197055b21a0a41da1115a07874e9c8e16670
Timestamp: 1767891955 Timestamp [UCT]: 2026-01-08 17:05:55 Age [y:d:h:m:s]: 00:019:07:04:26
Block: 1451469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13624 RingCT/type: yes/0
Extra: 018fb012aa909eff0ab78b755fb2d6197055b21a0a41da1115a07874e9c8e16670021100000002215bbf89000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fa456b290e0c4bb0c7419c9c571cb47e42100bda1bcc04d33ec2ec9a83c4a22 0.600000000000 1940481 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": 1451479, "vin": [ { "gen": { "height": 1451469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fa456b290e0c4bb0c7419c9c571cb47e42100bda1bcc04d33ec2ec9a83c4a22" } } ], "extra": [ 1, 143, 176, 18, 170, 144, 158, 255, 10, 183, 139, 117, 95, 178, 214, 25, 112, 85, 178, 26, 10, 65, 218, 17, 21, 160, 120, 116, 233, 200, 225, 102, 112, 2, 17, 0, 0, 0, 2, 33, 91, 191, 137, 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