Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce8f6f97ce01970f52df3ddc345a2f24347ec837b658b3e614c9f4cf6623881

Tx prefix hash: f4a745c6b4f5b93be8fe3aacba0f8c18dfbbc357f2417ecc5410c6fe3d52884b
Tx public key: 94ab7083ade93b7bc7d18c4019a73f521f07c90455ba56655a2cf45ad96d9b69
Timestamp: 1676207489 Timestamp [UCT]: 2023-02-12 13:11:29 Age [y:d:h:m:s]: 01:334:18:31:00
Block: 695384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500210 RingCT/type: yes/0
Extra: 0194ab7083ade93b7bc7d18c4019a73f521f07c90455ba56655a2cf45ad96d9b69021100000006835e4d22000000000000000000

1 output(s) for total of 3.047221756000 dcy

stealth address amount amount idx
00: e8d2d87ee0e317e1c00496468c008c9bb14136c85b7f4f073c7319d1523d1270 3.047221756000 1138339 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": 695394, "vin": [ { "gen": { "height": 695384 } } ], "vout": [ { "amount": 3047221756, "target": { "key": "e8d2d87ee0e317e1c00496468c008c9bb14136c85b7f4f073c7319d1523d1270" } } ], "extra": [ 1, 148, 171, 112, 131, 173, 233, 59, 123, 199, 209, 140, 64, 25, 167, 63, 82, 31, 7, 201, 4, 85, 186, 86, 101, 90, 44, 244, 90, 217, 109, 155, 105, 2, 17, 0, 0, 0, 6, 131, 94, 77, 34, 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